[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign juliusvonkohout for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

I think there are more pressing issues such as #3319, #3317 and many more that i will prioritize.

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This pull request has been automatically closed because it has not had recent activity.You can reopen the PR if you want.

We should actually consider decoupling, so kubeflow-katib, kubeflow-pipelines, kubeflow-dashboard etc. as namespace names.

We should actually consider decoupling, so kubeflow-katib, kubeflow-pipelines, kubeflow-dashboard etc. as namespace names.

@juliusvonkohout Any particular reason you want to separate system namespaces by the project? I think, it would be easier and better to install all control plane components into single kubeflow-system namespace.

We should actually consider decoupling, so kubeflow-katib, kubeflow-pipelines, kubeflow-dashboard etc. as namespace names.

@juliusvonkohout Any particular reason you want to separate system namespaces by the project? I think, it would be easier and better to install all control plane components into single kubeflow-system namespace.

CC @thesuperzapper I am mostly fine either way.